Hostname
partylite.pl
Last fetched
partylite.pl resolves to 100.21.200.117, announced in 100.20.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. partylite.pl is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:50:40 GMT
- Last seen on a feed
- Sun, 11 Oct 2026 07:24:45 GMT
Nutrition Label
Resolution chain
- 100.21.200.117
100.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 100.22.195.124
100.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 100.23.152.148
100.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 34.211.153.155
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 34.213.33.130
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 34.214.75.88
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 34.215.5.123
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 34.216.182.109
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.155.215.50
35.155.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.161.73.125
35.160.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.163.15.250
35.160.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.81.203.221
35.80.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.82.148.175
35.80.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.83.105.141
35.80.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.224.105.203
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.224.155.5
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.237.185.157
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.238.0.74
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.239.217.182
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.239.56.149
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
IPv6 resolution
No AAAA record for partylite.pl is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:internetx gmbh
- Registrant organisation
- partylite
Company
- Company
- PartyLite
- Headquarters
- Palo Alto, United States
Technology
PartyLite has been observed using 36 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
- Google Fonts API · font scripts
- Font Awesome · font scripts
- Google Analytics · intelligence and analytics
- Nginx · web servers
- Apache · web servers
- X-Content-Type-Options · web & portal technology
- Google Tag Manager · tag management
- Bootstrap · software framework
- Google Search Console · performance
- reCAPTCHA · captcha
- Amazon Web Services · cloud hosting
- X-XSS-Protection · security
- gstatic.com · content delivery network
- Microsoft 365 · email
- Piwik PRO Core · consent management
- iCIMS · applicant tracking systems
- cdnjs · content delivery network
- Element UI · javascript frameworks
Subdomains
Showing 4 of 4 subdomains (4 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for partylite.pl.
DKIM signing
No DKIM signing vendor is attributed to partylite.pl in WhisperGraph.
Nameservers
- ns10.managed-ip.com
- ns9.managed-ip.com
- ns11.managed-ip.info
- ns12.managed-ip.info
MX records
- partylite-pl.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from partylite.pl 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.