New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Eccouncil 312-50 Exam - Topic 4 Question 85 Discussion

Actual exam question for Eccouncil's 312-50 exam
Question #: 85
Topic #: 4
[All 312-50 Questions]

A certified ethical hacker is conducting a Whois footprinting activity on a specific domain. The individual is leveraging various tools such as Batch IP Converter and Whols Analyzer Pro to retrieve vital details but is unable to gather complete Whois information from the registrar for a particular set of dat

a. As the hacker, what might be the probable data model being utilized by the domain's registrar for storing and looking up

Who is information?

Show Suggested Answer Hide Answer
Suggested Answer: D

A thin Whois model is a type of data model that is used by some domain registrars for storing and looking up Whois information. In a thin Whois model, the registrar only stores the basic information about the domain, such as the domain name, the registrar name, the name servers, and the registration and expiration dates. The rest of the information, such as the contact details of the domain owner, the administrative contact, and the technical contact, is stored by the registry that manages the top-level domain (TLD) of the domain. For example, the registry for .com and .net domains is Verisign, and the registry for .org domains is Public Interest Registry.When a Whois lookup is performed on a domain that uses a thin Whois model, the registrar's Whois server only returns the basic information and refers the query to the registry's Whois server for the complete information1.

As a hacker, if you are unable to gather complete Whois information from the registrar for a particular set of data, it might be because the domain's registrar is using a thin Whois model and the registry's Whois server is not responding or providing the information. This could be due to various reasons, such as network issues, server errors, rate limits, privacy policies, or legal restrictions. Therefore, the probable data model being utilized by the domain's registrar for storing and looking up Whois information is a thin Whois model working correctly.


Differences Between Thin WHOIS vs Thick WHOIS -- OpenSRS Help & Support

by Luther at Jun 20, 2024, 02:05 AM

Limited Time Offer

25%

Off

Get Premium 312-50 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Daisy
3 months ago
Thick model usually has more data, so maybe that's it.
upvoted 0 times
...
Tresa
3 months ago
Surprised they can't get complete info, what's up with that?
upvoted 0 times
...
Francine
3 months ago
Definitely a malfunctioning server, no doubt!
upvoted 0 times
...
Desirae
4 months ago
I think it's a Thin Whois model, honestly.
upvoted 0 times
...
Shaniqua
4 months ago
Sounds like a Thick Whois model with issues.
upvoted 0 times
...
Clare
4 months ago
I’m leaning towards the thick Whois model being the issue here, but I could be mixing up the definitions.
upvoted 0 times
...
Tyra
4 months ago
This question reminds me of a practice question we did on Whois models. I feel like the thin model could be the right answer if the server is down.
upvoted 0 times
...
Jessenia
4 months ago
I think if the registrar's server is malfunctioning, it might indicate a thick Whois model, but I'm not completely confident about that.
upvoted 0 times
...
Bettina
5 months ago
I remember studying the differences between thick and thin Whois models, but I'm not sure which one applies here.
upvoted 0 times
...
Jesusa
5 months ago
Okay, I've got this. The key is to identify whether the registrar is using a thick or thin Whois model, and then determine if the issue is with a malfunctioning server or the model working correctly. I think I can work through this step-by-step and come up with the right answer.
upvoted 0 times
...
Bette
5 months ago
I'm a bit confused here. I know the thick and thin Whois models, but I'm not sure how to determine which one is being used based on the information provided. Maybe I should review my notes on Whois data models before attempting this question.
upvoted 0 times
...
Nan
5 months ago
Okay, let's see. If the registrar is using a thick Whois model, that means the full Whois data is stored on their servers, so a malfunctioning server could be the issue. But if it's a thin Whois model, the data might be distributed, so a server issue could also cause problems.
upvoted 0 times
...
Malcolm
5 months ago
Hmm, this seems like a tricky one. I'll need to think carefully about the different Whois models and how they might impact the registrar's data storage and lookup.
upvoted 0 times
...
Pauline
5 months ago
This seems like a good opportunity to apply my understanding of Whois data models. I'll carefully consider the details given and try to logically deduce the most likely scenario based on the registrar's ability to provide complete Whois information.
upvoted 0 times
...
Dannette
5 months ago
Okay, let me break this down. Blaming others (A) is definitely not the right way to show accountability. And never admitting mistakes (B) is just plain dishonest. Working according to your mood (D) is unprofessional. I think C is the clear winner here.
upvoted 0 times
...
Brande
5 months ago
Wait, I'm a bit confused. Do I need to use the Management Console to get the updates, or can I just download them directly?
upvoted 0 times
...
Beula
2 years ago
Is it just me, or do these Whois models sound like they're straight out of a spy novel? 'Thick' and 'thin' - what is this, a diet plan for hackers?
upvoted 0 times
Latanya
2 years ago
A: True, those terms do sound like they're from a spy novel!
upvoted 0 times
...
Emile
2 years ago
B: Or it could be a Thin Whois model working correctly.
upvoted 0 times
...
Misty
2 years ago
A: Maybe the registrar is using a Thick Whois model with a malfunctioning server.
upvoted 0 times
...
Kindra
2 years ago
C) Thin Whois model with a malfunctioning server
upvoted 0 times
...
Sabina
2 years ago
B) Thick Whois model working correctly
upvoted 0 times
...
King
2 years ago
A) Thick Whois model with a malfunctioning server
upvoted 0 times
...
...
Lauran
2 years ago
I think the issue might actually be with the server, regardless of the data model being used.
upvoted 0 times
...
Verona
2 years ago
I'm going with the thin Whois model working correctly. Why make it complicated when you can just keep it simple?
upvoted 0 times
Bernardo
2 years ago
B: I agree, it could be causing the issue with retrieving the complete Whois information.
upvoted 0 times
...
Lorriane
2 years ago
A: I think it's the Thick Whois model with a malfunctioning server.
upvoted 0 times
...
...
Shaniqua
2 years ago
But wouldn't a Thick Whois model make more sense for storing and looking up Whois information?
upvoted 0 times
...
Sharan
2 years ago
I disagree, I believe it could be a Thin Whois model with a malfunctioning server.
upvoted 0 times
...
Dianne
2 years ago
This is a tricky one. I'd say a thick Whois model with a malfunction. Those registrars can be so sneaky sometimes.
upvoted 0 times
...
Adelina
2 years ago
Hmm, I'm guessing it's a thin Whois model with a malfunctioning server. The registrar is probably trying to hide something.
upvoted 0 times
Michal
2 years ago
D: The registrar might be facing technical issues with their server.
upvoted 0 times
...
Larae
2 years ago
C: I think it's a thin Whois model with a malfunctioning server.
upvoted 0 times
...
Tracey
2 years ago
B: Maybe it's a thin Whois model working correctly.
upvoted 0 times
...
Elfriede
2 years ago
A: It could be a thick Whois model with a malfunctioning server.
upvoted 0 times
...
...
Shaniqua
2 years ago
I think the registrar might be using a Thick Whois model with a malfunctioning server.
upvoted 0 times
...

Save Cancel