Hostname
affbuzzads.com
Last fetched
affbuzzads.com resolves to 143.244.56.49, announced in 143.244.56.0/23 by CDN77 - Datacamp Limited in FR. affbuzzads.com is listed by 2 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 2 threat feeds. At least one source recommends blocking.
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:45:24 GMT
- Last seen on a feed
- Fri, 13 Nov 2026 20:25:31 GMT
Nutrition Label
Resolution chain
- 143.244.56.49
143.244.56.0/23 · CDN77 - Datacamp Limited · Paris, FR
- 143.244.56.50
143.244.56.0/23 · CDN77 - Datacamp Limited · Paris, FR
- 143.244.56.51
143.244.56.0/23 · CDN77 - Datacamp Limited · Paris, FR
- 143.244.56.53
143.244.56.0/23 · CDN77 - Datacamp Limited · Paris, FR
- 143.244.56.54
143.244.56.0/23 · CDN77 - Datacamp Limited · Paris, FR
- 143.244.56.56
143.244.56.0/23 · CDN77 - Datacamp Limited · Paris, FR
- 185.111.111.154
185.111.111.0/24 · CDNEXT - Datacamp Limited · Frankfurt am Main, DE
- 185.111.111.156
185.111.111.0/24 · CDNEXT - Datacamp Limited · Frankfurt am Main, DE
- 185.93.2.243
185.93.2.0/24 · CDN77 - Datacamp Limited · Paris, FR
- 185.93.2.248
185.93.2.0/24 · CDN77 - Datacamp Limited · Paris, FR
- 185.93.2.251
185.93.2.0/24 · CDN77 - Datacamp Limited · Paris, FR
- 185.93.3.244
185.93.3.0/24 · CDN77 - Datacamp Limited · Madrid, ES
- 79.127.134.225
79.127.134.0/24 · CDNEXT - Datacamp Limited · Villeurbanne, FR
- 79.127.134.226
79.127.134.0/24 · CDNEXT - Datacamp Limited · Villeurbanne, FR
- 79.127.134.227
79.127.134.0/24 · CDNEXT - Datacamp Limited · Villeurbanne, FR
- 79.127.134.230
79.127.134.0/24 · CDNEXT - Datacamp Limited · Villeurbanne, FR
- 79.127.237.104
79.127.236.0/23 · CDN77 - Datacamp Limited · London, GB
- 89.187.165.194
89.187.165.0/24 · CDN77 - Datacamp Limited · Zurich, CH
- 37.19.215.33
37.19.214.0/23 · CDN77 - Datacamp Limited · Madrid, ES
- 5.42.206.67
IPv6 resolution
Attribution
datacamp
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1950
- Registrant organisation
- pending backorder/auction delivery at www.dropcatch.com
- Contact emails
- affbuzzads.com@namebrightprivacy.com, domreg@domainholdingsmgmt.com, support@dropcatch.com
Company
- Company
- Affbuzzads
- Headquarters
- Passi, Philippines
Technology
Affbuzzads has been observed using 23 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:
- jQuery · javascript libraries
- Open Graph · content management system
- PHP · programming languages
- Google Fonts API · font scripts
- WordPress · blogs
- MySQL · database
- Font Awesome · font scripts
- Priority Hints · performance
- JSON-LD · frameworks and libraries
- RSS · content management system
- HTTP/3 · web & portal technology
- Cloudflare · content delivery network
- X-Content-Type-Options · web & portal technology
- oEmbed · audio, video, graphics
- Sitelinks Search Box · web tools and plugins
- Really Simple Discovery · miscellaneous
- X-XSS-Protection · security
- Yoast SEO · search engines
- Cloudflare CDN · content delivery network
- Cloudflare Bot Management · security
Subdomains
| Subdomain |
|---|
| ads.affbuzzads.com |
| ds.affbuzzads.com |
| tour.affbuzzads.com |
| wildcard.affbuzzads.com |
| www.affbuzzads.com |
Showing 5 of 5 subdomains (5 per page).
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for affbuzzads.com.
DKIM signing
No DKIM signing vendor is attributed to affbuzzads.com in WhisperGraph.
Nameservers
- ns1.dnsimple.com
- ns3.dnsimple.com
- ns2.dnsimple-edge.net
- ns4.dnsimple-edge.org
Threat-feed evidence
History
Related pages
Pivot from affbuzzads.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.