You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use this quick helper function in my app to first check if I can validate the email using the always-updated API and then fallback to my local package:
7:49:49 AM [vite] page reload src/lib/server/utils/isFakeEmail.ts (x4)
7:49:49 AM [vite-plugin-svelte] ssr compile done.
package files time avg
my-app 1 1.6ms 1.6ms
# Here I check email [email protected]
local: tpwlb.com
response: {
retcode: 200,
isFakeDomain: 'tpwlb.com',
details: {
provider: '10minutemail.com',
firstseen: 1676090000,
lastseen: 1676920000,
randomSubdomain: false
}
}
# Here I check email [email protected] <-- notice "sub" in domain
local: tpwlb.com
response: { retcode: 200, isFakeDomain: false, details: null }
The online response is correct when simply using the normal (fake) email address [email protected] but if I add a subdomain to the email address only my local response is correct.
Now - granted it doesn't affect my app, as I doubt many of these providers are using subdomains anyway, and thus they will never receive the verification email in order to gain access, but I wanted to flag this for a future update to the API.
The text was updated successfully, but these errors were encountered:
I use this quick helper function in my app to first check if I can validate the email using the always-updated API and then fallback to my local package:
And this is the response in the console:
The online response is correct when simply using the normal (fake) email address
[email protected]
but if I add a subdomain to the email address only my local response is correct.Now - granted it doesn't affect my app, as I doubt many of these providers are using subdomains anyway, and thus they will never receive the verification email in order to gain access, but I wanted to flag this for a future update to the API.
The text was updated successfully, but these errors were encountered: