Advertisement
Guest User

THE REAL TRUTH ABOUT U NIEL ANSELL #YOUTUBER EXPOSED

a guest
Sep 1st, 2018
401
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 23.75 KB | None | 0 0
  1.  
  2.  
  3.  
  4. THE REASON 4 THIS DOX MYBE BECAUSE THIS TRAITOR ONE OF THE VERY PEOPLE OF THE UNITED KINGDOM, RASCIT VILE JIHADI PEDOPHILIC SYMPOTHIZER !!!!
  5. NEIL ANSELL YOU HAVE MALIUOSLY CONDUCTED A CFRIME WITCH YOU HAVE INTENTLY USED TO SEAK FAME WEALTH AND THE GLORY OF TALKING ABOUTS A STORIE WITHOUT THE REAL TRUTH!!!
  6. AS WE SEE YOU ARE A YOUTUBER INFACT IF PEOPLE KNEW YOUR CRIMES & WHAT YOU ARE DOING WITH YOUR WEALTH,
  7. #COUGHS #CRYPTOCURRENCY INTO MARKETS WITCH WE FOUND LINKED TO JIHADI SUPPORTERS & TERRORIST GROUPS CHILD TRAFFICKING AND THE REST, WE WILL GET TO THAT..
  8. NOW PEOPLE WHOULD CALL ME A RACIST BUT WHAT THEY DONT UNDERSTAND THAT YOU ARE USING THE STORY OF 2 PEOPLE WHO
  9. WAS MURDERED IN COLD BLOOD.. NOT ONLy THAT BUT NEIL ANSELL FORT HE COULD TAKE IT UPON HIMSELVE AND MAKE UP THE GRAPE VINE ALONG THE WAY WITHOUT ASKING THE VERY FAMILY
  10. MEMBERS IF HE COULD REPORT OR INVESTIGATE ANYTHING WHAT SO EVER ...... THE HIGHLIGHTMOMENT THAT WE CANNOT 4 GET IS HOW DID HE ATTAIN THIS INFORMATION??
  11. THE ONLY WAY IS HIS WEALTH BUY INVESTING INTO DIRTY AND CORRUTED SERCRET SOCOITES , THE PHRASE CRYTO CURRENCY AND THE DARK WEB MARKETING SHARES IN WITCH WAS FOUND
  12. CONVERTED INTO RUPPEES WITCH WAS A " TRANSFER BY WESTERN UNION < IN THE UK " (SOUTHaFRICAN) CURRENCY EXCHANGES...
  13.  
  14. NIEL ANSELL REPORTED ON A MURDER ON HIS YOU TUBE CHANNEL (https://www.youtube.com/watch?v=pS3kK85usz0) (#Abandoned #urbex #abandonedexplorer)
  15. (https://www.youtube.com/channel/UCjn8bDuukMsi0tAzSSVTyNQ)
  16. Abandoned Double Murder House (He Killed Wife And Daughter) WHERE HE STATED THAT BOTH OF THE VICTIMS WAS KNIFED WITCH IS COMPLETLY WRONG!!!!!!! FAKE NEWS THIS INFORMATION
  17. HAS NEVER BEEN SHARED OR RELEASED BY ANY GOVERNMENT / FAMILY / BARRISTER ETC ,
  18. THE VICTIMS GOD REST THERE SOULS WHERE MURDERED IN COLD BLOOD BY A GUN WITCH WAS GIVEN BACK TO JOHN LOWE BY SUSSEX IN 2014.
  19. AFTER OVER 99+ CALLS IN STRESS FROM THE DAUGHTER (STACY BANNER) TELLING SUSSEX POLICE IN 2013/14 TOO REMOVE AND TAKE ALL (JOHN LOWES) FIREARMS AMMUMUNTION & FIRE ARMS LICIENSE.
  20. SUSSEX POLICE GAVE (JOHN LOWE) HIS WEAPONS BACK IN 13/14, JOHN LOWE MALIOUSLY MURDERED SHOT HIS WIFE AT BLANK RANGE AND WHILE HIS DAUGHTER LUCY RANG 999 4 HELP TRANSCRIPT ONLINE
  21. REAL 999 CALL WAS SHOT WHILE TRYING THE CALL THE POLICE GET HERSELF TO SAFTLY WHILE ASKING 4 THE POLICE OFFICER RAFFERTY KNOWS?!?!?
  22.  
  23. THE REAL QUESTION IS HOW THIS DRAWS OUT IS HOW DID YOU NIEL ANSELL GET THIUS INFOMATION OF THIS CASE ???
  24. MY SECOND QUESTION IS ARE YOU A INFORMER I.E WORK FOR THE GOVERNMENT?
  25. MY 3RD AND FINAL QUESTION IS.... WHAT AUTHORITEY DID YOU HAVE TO BE ON THOSE PERMISES 1ST AND FOREMOST??
  26.  
  27. IM NOT THE ONE TO CAST MARKERS ON PEOPLE HOW THEY SPEND THERE MONEY BUT WHEN YOU SMELL SOMETHING NOT RIGHT IN THE PIPE LINE YOU HAVE TO DELVE INTO THE RABBIT HOLE...
  28.  
  29. YOUR EMAILS ARE LINKED TOO (Abandoned Explorer - Efir.io
  30. https://efir.io/ar/youtube/Abandoned%20Explorer - Translate this page
  31. ???????. ????? ???????: Abandoned Explorer. Neilanselll@hotmail.co.uk ... exploring also known as urbex. Also guys checkout www.Forbiddenthirteen.co.uk ... )
  32. ON THIS CRYTOCURRENCY PAGE I FOUND LIKE AFEW OTHERS THAT YOU HAVE PLACED SERVAL INVESTMENTS & THE LIST OR ABRABIC SAUDIS PLUS SYMPOTHIZERS AS FRIENDS...
  33. THE QUESTION WOULD BE WHY ARE YOU HARVESTING AND INFLUENCING THESE PEOPLE AND THERE TERRORIST ACTIVITYS BECAUSE WE ALL KNOW THAT YOU HAVE SOLD YOUR SOUL AND ARE DANCING
  34. WITH THE DEVIL... YOU HAVE AQQUIRED INFOMATION WITCH HAS BROKE UK LAW ONE WITCH IS THE DATA PROTECTION ACT OF A FAMILYS RIGHTS...
  35. YOU HAVE PRODUCED FAKE NEWS LIKE THE MAIN STREAM MEDIA YOU HAVE WALKED & TREDDED ON THE WRONG GROUND!!!
  36. WHO DO YOU THINK YOU ARE SUPPORTING A CORRUPT ESTABLISHMENT A PEOPHILIC & TERRORISTIC ONE TOO HELP THEM FULLFIL THERE AGENDA 30!!
  37.  
  38. YOU ARE BEEN WATCH YOU ARE MONTITORED YOUR DAYS ARE MARKED !
  39.  
  40. THE LIST HERE WITCH IVE POSTED ARE DETAILS ON NIEL ANSELL .....
  41.  
  42. THIS GUY IS NOT WHAT AS HE SEEMS THERE IS A DARK PAST AND SO MUCH MORE TO THIS VILE PERSON...
  43.  
  44.  
  45.  
  46.  
  47. NEIL N. ANSELLL ALIAS N. ANSELL
  48.  
  49.  
  50. + 44 UK CODE
  51.  
  52. 330 133 0789
  53.  
  54. 073301330789
  55.  
  56. HIS MOBLIE TOOK ME TO Arkalyk
  57. 110000, Kazakhstan HMMM INTRESTING?
  58.  
  59. Weymouth, Shropshire
  60.  
  61. Weymouth, Dorset
  62.  
  63. Weymouth South west england
  64.  
  65. Location: United Kingdom
  66.  
  67. Links : FACEBOOK - TWITTER - TWITCH - TWITCH - SNAPCHAT - WORDPRESS - GOOGLE +
  68. https://en.gravatar.com/abandonedexplorer26 = WORDPRESS
  69. Instergram > https://www.instagram.com/abandoned_explor/
  70. User ID: 2316592200
  71. Username: abandoned_explor
  72. Full Name: Abandoned Explorer
  73.  
  74. Snapchat > https://www.snapchat.com/add/abandonedexp
  75.  
  76. https://twitter.com/AnsellNe > @ansellne => 2173714679 , Joined November 2013
  77.  
  78. https://www.facebook.com/Abandonedexplorer26/ numeric ID is: 1411016358949570
  79.  
  80. https://plus.google.com/104397515411250103672
  81.  
  82. https://www.pscp.tv/neilansell/1MnGnakZQZwKO
  83.  
  84. https://efir.io/ar/youtube/Abandoned%20Explorer
  85. https://exchange.efir.io/
  86. https://efir.io/ar/twitch
  87.  
  88. ? > http://www.data-email.info/view-email-list/Email-list-download-44667/44667.html
  89.  
  90. CRYTO CURRENCY MARKETING
  91. _____________________________________________________________________________________________
  92.  
  93. https://t.me/efirio
  94. Efir.io Chat (ex Qaazqaaz.com)
  95. 13 410 members
  96. Influencer marketing platform
  97. Web: Exchange.efir.io
  98. ICO End 2018, July, 31
  99. Channel: @qaazqaaz
  100. Chat: @efirio
  101. Platform: efir.io
  102. Twitter: twitter.com/Efir_qaazqaaz
  103. FB: fb.com/qaazqaazcom/
  104. WhitePaper: exchange.efir.io/assets/pdf/efir_io_WP-en.pdf
  105. VIEW GROUP
  106.  
  107. INVESTIGATE TELEGRAM
  108. _____________________________________________________________________________________________
  109.  
  110. Neilanselll@hotmail.co.uk
  111.  
  112.  
  113. Mail server found for domain:
  114. - eur.olc.protection.outlook.com (priority 10, ip address: 104.47.14.33)
  115.  
  116. Mailserver identification:
  117. AM5EUR02FT030.mail.protection.outlook.com Microsoft
  118. ESMTP MAIL Service ready at Sat, 1 Sep 2018 22:42:15 +0000
  119. Server doesn't allow e-mail address verification
  120.  
  121.  
  122. Field Name Type Description Example Data
  123. last Modified string Last modified date/time of Email Hippo record “Sat, 20 May 2017 12:13:36 GMT”
  124. expires string Date/time that this record expires from Email The cache “Mon, 19 Jun 2017 12:13:36 GMT”
  125. email string The email being queried “abuse@hotmail.com.br”
  126. tld string The Top Level Domain (TLD) of email being queried “com.br”
  127. domain string The domain of the email being queried “hotmail.com.br”
  128. subDomain string The sub domain (if any) of the email being queried null
  129. user string The user element of the email address “abuse”
  130. emailHashMd5 string MD5 hash of the email address “87da0257051ef17dd5580118ac2724f0”
  131. emailHashSha1 string SHA1 hash of the email address “c1a6e8994311d2fbe3add4c7168be86f23dab452”
  132. emailHashSha256 string SHA265 hash of the email address “29bf2669bc8ebc263eec23ed7859cb250352b9818471f2bc54b20f7e2f3b28c8”
  133.  
  134.  
  135. Disposition information
  136. Type info: disposition
  137.  
  138. Field Name Type Description Example Data
  139. isRole boolean Is a role address? (e.g. info@, sales@, postmaster@ true
  140. isFreeMail boolean Is a free mail provider? (e.g. hotmail, aol etc) true
  141. Example:
  142.  
  143. "disposition": {
  144. "isRole": true,
  145. "isFreeMail": true
  146. }
  147. Email verification. Syntax, DNS, mailbox
  148. Type info: emailVerification
  149.  
  150. Field Name Type Description Example Data
  151. syntaxVerification syntaxVerification Syntax Verification to RFC821 see example
  152. dnsVerification dnsVerification DNS Verification see example
  153. mailboxVerification mailboxVerification Mailbox Verification see example
  154. Example:
  155.  
  156. "emailVerification": {
  157. "syntaxVerification": {
  158. "isSyntaxValid": true,
  159. "reason": "Success"
  160. },
  161. "dnsVerification": {
  162. "isDomainHasDnsRecord": true,
  163. "isDomainHasMxRecords": true,
  164. "recordRoot": {
  165. "ipAddresses": [
  166. "65.55.118.92",
  167. "157.56.198.220"
  168. ]
  169. },
  170. "recordWww": {
  171. "ipAddresses": [
  172. "157.56.198.220"
  173. ]
  174. },
  175. "mxRecords": [
  176. {
  177. "preference": 5,
  178. "exchange": "mx1.hotmail.com",
  179. "ipAddresses": [
  180. "65.55.33.135",
  181. "104.44.194.236",
  182. "104.44.194.237",
  183. "104.44.194.235",
  184. "65.54.188.72",
  185. "65.54.188.126",
  186. "104.44.194.234",
  187. "65.55.37.88",
  188. "65.55.37.104",
  189. "104.44.194.233",
  190. "65.55.37.72",
  191. "65.55.92.184",
  192. "65.55.92.168",
  193. "207.46.8.167",
  194. "65.55.92.136",
  195. "104.44.194.232",
  196. "65.55.33.119",
  197. "104.44.194.231"
  198. ]
  199. },
  200. {
  201. "preference": 5,
  202. "exchange": "mx2.hotmail.com",
  203. "ipAddresses": [
  204. "104.44.194.235",
  205. "65.55.92.136",
  206. "65.54.188.94",
  207. "65.55.37.88",
  208. "207.46.8.167",
  209. "65.55.37.120",
  210. "104.44.194.237",
  211. "104.44.194.234",
  212. "104.44.194.236",
  213. "65.55.92.184",
  214. "104.44.194.233",
  215. "65.54.188.126",
  216. "104.44.194.231",
  217. "207.46.8.199",
  218. "104.44.194.232",
  219. "65.55.92.152",
  220. "65.55.37.104",
  221. "65.55.33.135",
  222. "65.54.188.72"
  223. ]
  224. },
  225. {
  226. "preference": 5,
  227. "exchange": "mx3.hotmail.com",
  228. "ipAddresses": [
  229. "65.55.37.120",
  230. "65.55.92.136",
  231. "65.55.92.152",
  232. "104.44.194.234",
  233. "65.55.33.119",
  234. "65.55.92.168",
  235. "104.44.194.232",
  236. "65.55.37.72",
  237. "104.44.194.235",
  238. "104.44.194.236",
  239. "65.54.188.94",
  240. "65.54.188.110",
  241. "207.46.8.167",
  242. "104.44.194.237",
  243. "104.44.194.231",
  244. "65.55.37.104",
  245. "104.44.194.233",
  246. "65.54.188.72",
  247. "207.46.8.199"
  248. ]
  249. },
  250. {
  251. "preference": 5,
  252. "exchange": "mx4.hotmail.com",
  253. "ipAddresses": [
  254. "65.55.37.120",
  255. "65.54.188.110",
  256. "104.44.194.235",
  257. "104.44.194.232",
  258. "65.55.92.168",
  259. "207.46.8.199",
  260. "65.54.188.94",
  261. "65.55.92.152",
  262. "104.44.194.237",
  263. "65.55.33.135",
  264. "65.55.37.88",
  265. "104.44.194.234",
  266. "65.55.92.184",
  267. "104.44.194.233",
  268. "104.44.194.231",
  269. "65.55.37.72",
  270. "104.44.194.236",
  271. "65.55.33.119"
  272. ]
  273. }
  274. ],
  275. "txtRecords": [
  276. "\"v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com ~all\""
  277. ]
  278. },
  279. "mailboxVerification": {
  280. "result": "Bad",
  281. "reason": "MailboxDoesNotExist"
  282. }
  283. }
  284.  
  285. Field Name Type Description Example Data
  286. isDomainHasDnsRecord boolean Does the dmain have any DNS records? true
  287. isDomainHasMxRecords boolean Does the domain have any MX records? true
  288. recordRoot record Details of root A record for domain see example
  289. recordWww record Details of records for WWW subdomain see example
  290. mxRecords List of mxrecord All MX records for domain see example
  291. txtRecords List of string All TXT records for domain “”v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com ~all”“
  292.  
  293. "dnsVerification": {
  294. "isDomainHasDnsRecord": true,
  295. "isDomainHasMxRecords": true,
  296. "recordRoot": {
  297. "ipAddresses": [
  298. "65.55.118.92",
  299. "157.56.198.220"
  300. ]
  301. },
  302. "recordWww": {
  303. "ipAddresses": [
  304. "157.56.198.220"
  305. ]
  306. },
  307. "mxRecords": [
  308. {
  309. "preference": 5,
  310. "exchange": "mx1.hotmail.com",
  311. "ipAddresses": [
  312. "65.55.33.135",
  313. "104.44.194.236",
  314. "104.44.194.237",
  315. "104.44.194.235",
  316. "65.54.188.72",
  317. "65.54.188.126",
  318. "104.44.194.234",
  319. "65.55.37.88",
  320. "65.55.37.104",
  321. "104.44.194.233",
  322. "65.55.37.72",
  323. "65.55.92.184",
  324. "65.55.92.168",
  325. "207.46.8.167",
  326. "65.55.92.136",
  327. "104.44.194.232",
  328. "65.55.33.119",
  329. "104.44.194.231"
  330. ]
  331. },
  332. {
  333. "preference": 5,
  334. "exchange": "mx2.hotmail.com",
  335. "ipAddresses": [
  336. "104.44.194.235",
  337. "65.55.92.136",
  338. "65.54.188.94",
  339. "65.55.37.88",
  340. "207.46.8.167",
  341. "65.55.37.120",
  342. "104.44.194.237",
  343. "104.44.194.234",
  344. "104.44.194.236",
  345. "65.55.92.184",
  346. "104.44.194.233",
  347. "65.54.188.126",
  348. "104.44.194.231",
  349. "207.46.8.199",
  350. "104.44.194.232",
  351. "65.55.92.152",
  352. "65.55.37.104",
  353. "65.55.33.135",
  354. "65.54.188.72"
  355. ]
  356. },
  357. {
  358. "preference": 5,
  359. "exchange": "mx3.hotmail.com",
  360. "ipAddresses": [
  361. "65.55.37.120",
  362. "65.55.92.136",
  363. "65.55.92.152",
  364. "104.44.194.234",
  365. "65.55.33.119",
  366. "65.55.92.168",
  367. "104.44.194.232",
  368. "65.55.37.72",
  369. "104.44.194.235",
  370. "104.44.194.236",
  371. "65.54.188.94",
  372. "65.54.188.110",
  373. "207.46.8.167",
  374. "104.44.194.237",
  375. "104.44.194.231",
  376. "65.55.37.104",
  377. "104.44.194.233",
  378. "65.54.188.72",
  379. "207.46.8.199"
  380. ]
  381. },
  382. {
  383. "preference": 5,
  384. "exchange": "mx4.hotmail.com",
  385. "ipAddresses": [
  386. "65.55.37.120",
  387. "65.54.188.110",
  388. "104.44.194.235",
  389. "104.44.194.232",
  390. "65.55.92.168",
  391. "207.46.8.199",
  392. "65.54.188.94",
  393. "65.55.92.152",
  394. "104.44.194.237",
  395. "65.55.33.135",
  396. "65.55.37.88",
  397. "104.44.194.234",
  398. "65.55.92.184",
  399. "104.44.194.233",
  400. "104.44.194.231",
  401. "65.55.37.72",
  402. "104.44.194.236",
  403. "65.55.33.119"
  404. ]
  405. }
  406. ],
  407. "txtRecords": [
  408. "\"v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com ~all\""
  409. ]
  410. }
  411.  
  412.  
  413. "infrastructure": {
  414. "mail": {
  415. "serviceTypeId": "Hotmail",
  416. "mailServerLocation": "US",
  417. "smtpBanner": "220 SNT004-MC9F19.hotmail.com Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited. Other restrictions are found at http://privacy.microsoft.com/en-us/anti-spam.mspx. Sat, 20 May 2017 05:13:34 -0700"
  418. },
  419. "web": {
  420. "hasAliveWebServer": true
  421. }
  422. }
  423.  
  424. Mail infrastructure
  425. Type info: mailInfrastructure
  426.  
  427. Field Name Type Description Example Data
  428. serviceTypeId serviceTypeId Service Type Identifier. “Hotmail”
  429. mailServerLocation string Mail server location. 2 digit ISO code. “US”
  430. smtpBanner string SMTP banner received on connect to mail server. see example
  431.  
  432. Example:
  433.  
  434. "mail": {
  435. "serviceTypeId": "Hotmail",
  436. "mailServerLocation": "US",
  437. "smtpBanner": "220 SNT004-MC9F19.hotmail.com Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited. Other restrictions are found at http://privacy.microsoft.com/en-us/anti-spam.mspx. Sat, 20 May 2017 05:13:34 -0700"
  438. }
  439. Service type identifier
  440. Type info: serviceTypeId
  441.  
  442. Other: Service not of pre-defined list of known types.
  443. Aol: AOL.
  444. Hotmail: Hotmail.
  445. Gmail: Gmail.
  446. GoogleForBiz: Google for business.
  447. MessageLabs: Symantec message labs.
  448. Net4Sec: Net4Sec.
  449. Office365: Microsoft Office 365.
  450. Yahoo: Yahoo.
  451. UceProtect: UCE Protect.
  452. Web infrastructure
  453. Type info: webInfrastructure
  454.  
  455. Email Hippo performs a PING to establish whether a domain has a working web server / web site. A domain without a working website can be an indicator of low quality email domains.
  456.  
  457. Field Name Type Description Example Data
  458. hasAliveWebServer boolean Determines if domain has a web server that responds to PING. true
  459. Example:
  460.  
  461. "web": {
  462. "hasAliveWebServer": true
  463. }
  464. Send assessment
  465. Type info: sendAssess
  466.  
  467. Email Hippo performs an assessment of the risk associated with sending email to the email address queried. The overall score is based on a number of factors including:
  468.  
  469. If the domain is determined to be a DEA
  470. If the mailbox is verified as ‘Ok’ or ‘Good’
  471. Whether the email domain is listed in third party lists (e.g. SpamHaus)
  472. Whether the domain is determined to be FreeMail or is a role address
  473. Whether the domain has a working web site
  474. Field Name Type Description Example Data
  475. inboxQualityScore decimal Inbox quality score. 0.1
  476. sendRecommendation sendAssesType Send recommendation. “DoNotSend”
  477. Send recommendation
  478. None: No recommendation.
  479. SafeToSend: Safe to send email. Minimal risk of hard bounces or complaints.
  480. DoNotSend: Do not send. Hight risk of hard bounce and complaints.
  481. RiskyToSend: Sending to this email address is risky. Hard bounces and complaints are possible. Send at your own risk.
  482. Example:
  483.  
  484. "sendAssess": {
  485. "inboxQualityScore": 0.1,
  486. "sendRecommendation": "DoNotSend"
  487. }
  488. Spam assessment
  489. Type info: spamAssess
  490.  
  491. Email Hippo performs an assesment of the risk associated with receiving email from the address queried. The overall score is based on a number of factors from the table below.
  492.  
  493. Field Name Type Description Example Data
  494. isDisposableEmailAddress boolean Is the email domain a DEA? false
  495. isDarkWebEmailAddress boolean Is the email address domain hosted in the Dark Web? false
  496. isGibberishDomain boolean Is the email address domain deemed to be gibberish text? false
  497. isGibberishUser boolean Is the email address user deemed to be gibberish text? false
  498. domainRiskScore decimal General risk score of email address domain. 0
  499. formatRiskScore decimal Format risk score of email address. 0
  500. profanityRiskScore decimal Profanity risk score of email address. 0
  501. overallRiskScore decimal Overall risk score for spam from this email address. 0
  502. actionRecomendation actionRecommendationType What action should you take if receiving email from email address. “Allow”
  503. blockLists List of blockList Blocklists. see example
  504. Example:
  505.  
  506. "spamAssess": {
  507. "isDisposableEmailAddress": false,
  508. "isDarkWebEmailAddress": false,
  509. "isGibberishDomain": false,
  510. "isGibberishUser": false,
  511. "domainRiskScore": 0,
  512. "formatRiskScore": 0,
  513. "profanityRiskScore": 0,
  514. "overallRiskScore": 0,
  515. "actionRecomendation": "Allow",
  516. "blockLists": [
  517. {
  518. "blockListName": "spamhaus",
  519. "isListed": false,
  520. "listedReason": null,
  521. "listedMoreInfo": null
  522. }
  523. ]
  524. }
  525. Blocklists
  526. Type info: List of blockList
  527.  
  528. Email Hippo includes references to third party spam block lists to enrich it’s own email verification information.
  529.  
  530. Initially (on launch of v3), we include references to SpamHaus Domain Block List (DBL).
  531.  
  532. Note
  533.  
  534. Email Hippo may add additional data sources for blocklists in the future.
  535.  
  536. Field Name Type Description Example Data
  537. blockListName string Name of block list. “spamhaus”
  538. isListed boolean Is the email address domain listed in the block list? true
  539. listedReason string If the email address domain is listed in the block list, then why? “127.0.1.2”
  540. listedMoreInfo string Any additional information provided from the block list on reason(s) “https://www.spamhaus.org/query/domain/dbltest.com”
  541. Example:
  542.  
  543. "blockLists": [
  544. {
  545. "blockListName": "spamhaus",
  546. "isListed": true,
  547. "listedReason": "127.0.1.2",
  548. "listedMoreInfo": "https://www.spamhaus.org/query/domain/dbltest.com"
  549. }
  550. ]
  551. Spam trap assessment
  552. Type info: List of spamTrapAssess
  553.  
  554. Email Hippo maintains a list of known Spam Trap.
  555.  
  556. Field Name Type Description Example Data
  557. isSpamTrap boolean Is this email address a known spam trap? true
  558. spamTrapDescriptor string Description of spam trap. “uceprotect”
  559. Example:
  560.  
  561. "spamTrapAssess": {
  562. "isSpamTrap": true,
  563. "spamTrapDescriptor": "uceprotect"
  564. }
  565. Email Hippo Trust Score
  566. Type info: List of hippoTrust
  567.  
  568. For email verification and data enrichment performed to the ‘More’ level, Email Hippo supplies a Trust Score.
  569.  
  570. About the Email Hippo Trust Score Email Hippo created the Trust Score to provide an ‘at a glance’ determination of quality from the point of view of drilling deeper than just the email address itself.
  571.  
  572. Email Hippo Trust Score is designed to answer a fundamental question posed from the perspective of a business owner, merchant, data broker or lean generation service:
  573.  
  574. How much can I trust the person associated with this email address?
  575.  
  576. The Trust Score takes dozens of metrics and signals into consideration when making this assesment and providing the final score.
  577.  
  578. Field Name Type Description Example Data
  579. score decimal How much can I trust the person associated with this email address? 0.1
  580. level trustLevelType `Hippo Trust Level`_. “Low”
  581. Trust level
  582. Type info: trustLevelType
  583.  
  584. None: No information on trust.
  585. Low: Low trust level.
  586. Medium: Medium trust level.
  587. High: High trust level.
  588. Example:
  589.  
  590. "hippoTrust": {
  591. "score": 0.1,
  592. "level": "Low"
  593. }
  594. Social information
  595. Type info: social
  596.  
  597. Email Hippo can provide social data. On initial launch of v3, Gravatar information is supplied.
  598.  
  599. Field Name Type Description Example Data
  600. social social Social information associated with email address see example
  601. Example:
  602.  
  603. "social": {
  604. "gravatar": {
  605. "imageUrl": "//www.gravatar.com/avatar/87da0257051ef17dd5580118ac2724f0",
  606. "profileUrl": "//www.gravatar.com/87da0257051ef17dd5580118ac2724f0"
  607. }
  608. }
  609. Performance information
  610. Type info: performance
  611.  
  612. Detailed performance metrics are provided for all queries. All timings are expressed in milliseconds.
  613.  
  614. Field Name Type Description Example Data
  615. syntaxCheck integer Processing time to check syntax of email address. see example
  616. dnsLookup integer Processing time to gather and check DNS of email address. see example
  617. spamAssessment integer Processing time to assess email address for spam behavior. see example
  618. mailboxVerification integer Processing time to check mail box of email address. see example
  619. webInfrastructurePing integer Processing time to PING web site of email address. see example
  620. other integer Processing time for miscellaneous processing of email address. see example
  621. overallExecutionTime integer Total processing time. see example
  622. Example:
  623.  
  624. "performance": {
  625. "syntaxCheck": 0,
  626. "dnsLookup": 250,
  627. "spamAssessment": 0,
  628. "mailboxVerification": 5348,
  629. "webInfrastructurePing": 0,
  630. "other": 0,
  631. "overallExecutionTime": 5598
  632. }
  633. Response header
  634. HTTP status codes
  635. In additional to the application level codes (see Primary Result Codes and Secondary Reason Codes) returned in the HTTP message body, HTTP status codes are returned in the HTTP header.
  636.  
  637. 200: Call successful.
  638. 400: Bad request. The server could not understand the request. Perhaps missing a license key or an email to check? Conditions that lead to this error are: No license key supplied, no email address supplied, email address > 255 characters, license key in incorrect format.
  639. 401: Possible reasons: The provided license key is not valid, the provided license key has expired, you have reached your quota capacity for this account, this account has been disabled.
  640. 429: Too many requests. See Concurrency for further information.
  641. 50x: An error occurred on the server. Possible reasons are: license key validation failed or a general server fault.
  642.  
  643.  
  644. Last Modified Sat, 01 Sep 2018 22:44:36 GMT
  645. Expires Tue, 29 Aug 2028 22:44:36 GMT
  646. Email neilanselll@hotmail.co.uk
  647. TLD co.uk
  648. Domain hotmail.co.uk
  649. Sub Domain
  650. User neilanselll
  651.  
  652. Date checked: Sat, 01 Sep 2018 22:44:36 GMT
  653. Detailed DNS Information
  654. Has DNS record? True
  655. Has MX records? True
  656. Root A record 204.79.197.208
  657. WWW record 204.79.197.209
  658. MX records
  659. Exchange Preference
  660. eur.olc.protection.outlook.com 10
  661.  
  662. TXT records
  663. Item
  664. "v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com
  665.  
  666. SMTP Banner 220 VE1EUR01FT034.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sat, 1 Sep 2018 22:44:35 +0000
  667.  
  668.  
  669. Spammy signals for email address
  670. Is a DEA? False
  671. Is a dark web mail provider? False
  672. Is a gibberish domain? False
  673. Is a gibberish user? False
  674. Domain risk score (0-10) 3
  675. Format risk score (0-10) 0
  676. Profanity risk score (0-10) 0
  677. Overall risk score (0-10) 0.8
  678. Receive messages from this email? Allow
  679. Blocklists
  680.  
  681. MX record found: eur.olc.protection.outlook.com (Priority 10)
  682. Connecting to eur.olc.protection.outlook.com
  683. Connected to eur.olc.protection.outlook.com
  684. Dialog with eur.olc.protection.outlook.com ok
  685. ------------------------------------------------------------
  686. 220 VE1EUR03FT051.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sat, 1 Sep 2018 22:56:36 +0000
  687. HELO verifyemailaddress.org
  688. 250 VE1EUR03FT051.mail.protection.outlook.com Hello [209.126.119.123]
  689. MAIL FROM: <noreply@verifyemailaddress.org>
  690. 250 2.1.0 Sender OK
  691. RCPT TO: <Neilanselll@hotmail.co.uk>
  692. 250 2.1.5 Recipient OK
  693. QUIT
  694. 221 2.0.0 Service closing transmission channel
  695. ------------------------------------------------------------
  696. Email address Neilanselll@hotmail.co.uk accepted
  697.  
  698.  
  699. https://www.verifyemailaddress.org/goto/evresult/Neilanselll@hotmail.co.uk CLEARLY THIS STATES THAT THIS PERSONS ISNT REAL & IS A FAKE!!
  700.  
  701.  
  702.  
  703.  
  704.  
  705.  
  706.  
  707.  
  708.  
  709. YOU WANT THE TRUTH OF THE REAL STORIE THE REAL PERSONS NAME IS IN THIS INFORMATION
  710.  
  711. DO NOT LISTEN TO THIS IDIOT NIEL ANSEL !!!
  712.  
  713. WE ARE WATCHING YOU NEIL YOU MADE YOURSELF A TARGET AND EXCEPT YOUR FATE
  714.  
  715. UNDERCOVER FAKE PEDOPHILIC JIHADI BRISTISH TRATOR !
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement